feat: social account linking by luciorubeens · Pull Request #515 · allinbits/dither.chat

luciorubeens · 2026-03-02T22:14:06Z

Summary

Added social account linking so users can map their external username/handle to their address.
It works through a proof verification similar to keybase.io: users post a message containing their address on the social platform, then submit the proof URL. The backend checks if the proof is valid and updates the status.
For now it is integrated with X (Twitter) and GitHub. More providers can be added later.
Updated the backend API to return the associated social handles together with feed, replies, and notifications data when available.

Fixes #508

Dither.Demo.mp4

Screenshots


Failed verification with retry option


Profile with multiple verified social handles

jeronimoalbi · 2026-03-03T09:48:54Z

Great work 👍

Something we should consider is to use names like lucio@x or lucio@github instead. Eventually we might want to integrate with Gno.land names registry for example, when the feature is available, and those might eventually be the ones without suffix.

luciorubeens · 2026-03-03T11:13:32Z

@jeronimoalbi Yes, we're already storing it that way. The only difference is that the Username component will render it as a styled UI badge.

To tag someone, you’ll need to use the user@platform format.

Btw we also need to update the /profile endpoint to support username resolution.

luciorubeens · 2026-03-19T12:12:08Z

The PR is ready for review. Supporting tagging other users while posting will be the next step.

One thing to note before deploying: we’ll propably need to introduce migrations using Drizzle (https://orm.drizzle.team/docs/migrations). Currently, we're just pushing the schema directly to the database (https://github.com/allinbits/dither.chat/blob/main/packages/api-main/package.json#L17).

jeronimoalbi · 2026-03-25T15:15:12Z

packages/lib-api-types/src/utils.ts

+ * matches the code verified against the proof tweet.
+ */
+export function getSocialProofCode(address: string): string {
+  const withoutPrefix = address.replace(/^[a-z]+1/, '');


Why are you using a regular expression instead of slice(5)?

jeronimoalbi · 2026-03-25T15:26:36Z

packages/reader-main/src/messages/social.ts

+export async function LinkSocial(action: ActionWithData): Promise<ResponseStatus> {
+  try {
+    const [username, platform, proofUrl] = extractMemoContent(action.memo, 'dither.LinkSocial');
+    const postBody: { hash: string; from: string; username: string; platform: string; proof_url: string; timestamp: string } = {


Suggested change

const postBody: { hash: string; from: string; username: string; platform: string; proof_url: string; timestamp: string } = {

const postBody: Posts.SocialProofBody = {

jeronimoalbi · 2026-03-25T15:28:48Z

packages/reader-main/src/messages/social.ts

+/* eslint-disable ts/no-namespace */
+import type { ActionWithData, ResponseStatus } from '../types/index';


Importing it allows to use Posts.SocialProofBody in the next comment:

Suggested change

/* eslint-disable ts/no-namespace */

import type { ActionWithData, ResponseStatus } from '../types/index';

/* eslint-disable ts/no-namespace */

import type { Posts } from '@atomone/dither-api-types';

import type { ActionWithData, ResponseStatus } from '../types/index';

The space in between the imports is for consistency with all of the other files in the same folder than this one.

jeronimoalbi · 2026-03-25T15:44:37Z

packages/api-main/README.md

+## Social Verification
+
+Social username verification is asynchronous:


Suggested change

## Social Verification

Social username verification is asynchronous:

## Social Verification

Verification is done to link an AtomOne address to one or more social account usernames.

Social username verification is asynchronous:

jeronimoalbi · 2026-03-25T16:07:54Z

packages/reader-main/src/messages/social.ts

+      hash: action.hash,
+      from: action.sender,
+      username,
+      platform,


We should validate that platform is valid before anything else I think, if it fails we could send an internal message to the user.

jeronimoalbi · 2026-03-30T14:28:58Z

packages/api-main/src/gets/socialLinks.ts

+    if (tokenAddress && tokenAddress.toLowerCase() === address) {
+      isOwner = true;
+    }


Maybe?

Suggested change

if (tokenAddress && tokenAddress.toLowerCase() === address) {

isOwner = true;

}

isOwner = (tokenAddress && tokenAddress.toLowerCase() === address)

jeronimoalbi · 2026-03-30T14:38:36Z

packages/api-main/src/posts/social.ts

+  // Verification runs in background, we don't want to block the API response.
+  // Future improvement: if we had a job queue system, we could push a job here instead of this.
+  verifyLink(insertedId, body.platform.toLowerCase(), body.proof_url, body.from.toLowerCase(), body.username.toLowerCase()).catch(
+    err => console.error(`verifySocialLink error for id=${insertedId}:`, err),


It would be a good idea to send a notification to the user with the failure reason, otherwise it might happen that verification fails and user ends up only seeing the social link pending for a long time.

It might be worth considering maybe using a scheduled GitHub CI workflow that runs from time to time and tries to verify accounts created a while ago that failed to be verified within the max retries threshold.

jeronimoalbi · 2026-03-30T14:42:20Z

packages/api-main/src/social/verify.ts

+const MAX_RETRIES = 3;
+const INITIAL_DELAY_MS = 2000; // 2 seconds, doubles each retry


WDYT about increasing max retries to 7 or 10 retries?

Also maybe even increasing the initial delay a bit. Increasing both has the potential to work if there are long hickups with a service.

jeronimoalbi · 2026-03-30T14:43:58Z

packages/api-main/src/social/verify.ts

+ * Never throws — all errors are caught and result in a 'failed' DB update.
+ */
+export async function verifyLink(
+  id: number,


Maybe change id to socialLinkId for clarity?

jeronimoalbi · 2026-03-30T14:47:17Z

packages/api-main/src/social/verify.ts

+    if (await isHandleAlreadyClaimed(username, platform, id)) {
+      await getDatabase()
+        .update(SocialLinksTable)
+        .set({ status: STATUS_FAILED, error_reason: ERROR_REASON_HANDLE_ALREADY_CLAIMED })
+        .where(eq(SocialLinksTable.id, id));
+      return;
+    }


This should provably be the first thing to do for both cases when this function is called to make sure handle is not claimed before doing anything else. It would remove the duplicated code too.

jeronimoalbi · 2026-03-30T14:54:10Z

packages/api-main/src/social/verify.ts

+        eq(SocialLinksTable.handle, handle),
+        eq(SocialLinksTable.platform, platform),
+        eq(SocialLinksTable.status, STATUS_VERIFIED),
+        ne(SocialLinksTable.id, excludeId),


Is the excludeId really needed? If the handle is already claimed it wouldn't matter who did it, isn't it?

jeronimoalbi · 2026-03-30T15:23:31Z

The PR is ready for review. Supporting tagging other users while posting will be the next step.

One thing to note before deploying: we’ll propably need to introduce migrations using Drizzle (https://orm.drizzle.team/docs/migrations). Currently, we're just pushing the schema directly to the database (https://github.com/allinbits/dither.chat/blob/main/packages/api-main/package.json#L17).

It's definitely needed 👍

jeronimoalbi · 2026-03-31T09:02:13Z

packages/frontend-main/src/components/users/Username.vue

+  return providers.find(p => p.id === platform.value) ?? null;
+});
+
+const display = computed(() => handle.value ? `@${handle.value}` : shorten(props.userAddress || '...............', 8, 4));


The "@" prefix could be removed, otherwise username would look like @elon@x:

Suggested change

const display = computed(() => handle.value ? `@${handle.value}` : shorten(props.userAddress || '...............', 8, 4));

const display = computed(() => handle.value ? `${handle.value}` : shorten(props.userAddress || '...............', 8, 4));

jeronimoalbi · 2026-03-31T09:12:38Z

packages/frontend-main/src/views/Profile/ProfileViewWrapper.vue


-      <Tabs v-if="wallet.loggedIn.value" :tabs="tabs" layout="fill" class="border-t" />
+      <!-- Social Accounts -->
+      <SocialAccountsPanel


WDYT about moving the verification forms to settings? It seems a bit off in the user profile page.

Profile could display the already verified accounts only.

luciorubeens added 4 commits February 19, 2026 09:05

feat(social): add social proof linking and verification flow

e70244d

refactor: better ui and github implementation

ea1fbdb

Merge remote-tracking branch 'origin/main' into feat/social-network-name

26a8603

fix: localnet leftover

b950685

github-project-automation bot added this to Dither Community Board Mar 2, 2026

github-project-automation bot moved this to Ready to Build in Dither Community Board Mar 2, 2026

luciorubeens added 3 commits March 18, 2026 21:13

feat: polish verification UI

e3c16eb

chore: test token

111d559

fix: lint failing

98dbfe7

Kouteki assigned luciorubeens Mar 19, 2026

Kouteki requested a review from jeronimoalbi March 19, 2026 12:30

jeronimoalbi reviewed Mar 27, 2026

View reviewed changes

jeronimoalbi reviewed Mar 30, 2026

View reviewed changes

jeronimoalbi reviewed Mar 31, 2026

View reviewed changes

	const postBody: { hash: string; from: string; username: string; platform: string; proof_url: string; timestamp: string } = {
	const postBody: Posts.SocialProofBody = {

		/* eslint-disable ts/no-namespace */
		import type { ActionWithData, ResponseStatus } from '../types/index';

		## Social Verification

		Social username verification is asynchronous:

		const MAX_RETRIES = 3;
		const INITIAL_DELAY_MS = 2000; // 2 seconds, doubles each retry

	const display = computed(() => handle.value ? `@${handle.value}` : shorten(props.userAddress \|\| '...............', 8, 4));
	const display = computed(() => handle.value ? `${handle.value}` : shorten(props.userAddress \|\| '...............', 8, 4));

Conversation

luciorubeens commented Mar 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots

Uh oh!

jeronimoalbi commented Mar 3, 2026

Uh oh!

luciorubeens commented Mar 3, 2026

Uh oh!

luciorubeens commented Mar 19, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jeronimoalbi commented Mar 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

luciorubeens commented Mar 2, 2026 •

edited

Loading

jeronimoalbi commented Mar 30, 2026 •

edited

Loading